Add memory-safety guideline#4654
Merged
Merged
Conversation
Contributor
|
Please, extend this list accordingly: Also, add the new list item to the selected items' list: Yes, you're right, this should be added dynamically in the future :) Also, the severity of some checkers are changed (from medium to high, for example). This breaks some tests: https://github.com/Ericsson/codechecker/actions/runs/17100480035/job/48495383987?pr=4654 Thank you! |
bruntib
pushed a commit
that referenced
this pull request
Sep 19, 2025
* add memory-safety guideline * add some Clang warnings, revert severity changes, add stats
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new guideline,
memory-safety, which can be useful for developers who are interested in catching specifically memory-safety bugs.Furthermore, my suggestion (included in the PR) is to raise
unix.MismatchedDeallocatorandunix.MalloctoHIGHseverity. The former always leads to UB on true positives, and the latter almost always.